chore(deps): bump k8s.io/client-go from 0.30.3 to 0.34.1 #1644
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=80&v=4){kind=small}
dependabot
bot
force-pushed
the
dependabot/go_modules/k8s.io/client-go-0.34.1
branch
from
055d6d1 to
5b17526
Compare
dependabot
bot
force-pushed
the
dependabot/go_modules/k8s.io/client-go-0.34.1
branch
from
5b17526 to
db37d0d
Compare
dependabot
bot
force-pushed
the
dependabot/go_modules/k8s.io/client-go-0.34.1
branch
from
db37d0d to
9f8ab99
Compare
|
@dependabot rebase |
dependabot
bot
force-pushed
the
dependabot/go_modules/k8s.io/client-go-0.34.1
branch
from
9f8ab99 to
9885391
Compare
Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.30.3 to 0.34.1. - [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md) - [Commits](kubernetes/client-go@v0.30.3...v0.34.1) --- updated-dependencies: - dependency-name: k8s.io/client-go dependency-version: 0.34.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/go_modules/k8s.io/client-go-0.34.1
branch
from
9885391 to
12e7f84
Compare
|
A single node development cluster (infra-pr-1644) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: Further Development☕ If you make changes, you can commit and push and CI will take care of updating the development cluster. 🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
2 participants
Bumps k8s.io/client-go from 0.30.3 to 0.34.1.
Commits
d033c49Update dependencies to v0.34.1 tag97396afMerge remote-tracking branch 'origin/master' into release-1.345f737f3clarify that staging repos are automatically published0b8655badd pointer to CONTRIBUTING.md for more details on contributing, clarify read...c00384clink to what a staging repository isb53b1f8docs: clarify that this is a staging repository and not for direct contributions42e6182KEP-5075: generated codes from make updateda11948Merge pull request #130653 from yliaog/master3b7d818extended resource backed by DRA: codegenbb11581Merge pull request #130160 from KobayashiD27/dra-device-binding-conditionsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)